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/1676674/cc3301-ble-hci-receiver-test-error/6481213Fri, 11 Sep 2026 16:34:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6ae912a6-1681-409d-ac1c-6cf3fce83f9fBLiuKonnichiwa Reiji-san, I&#39;ll look into this and send something over to you. Thanks.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1670104/cc3301-cc3301-band-edge-emissions/6481001Fri, 11 Sep 2026 13:48:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4f682075-80be-40ec-bb9c-6a0dea09d392Juha H&#228;m&#228;l&#228;inenDisabling the logger was a separate test, it is not included in the conf file I attached yesterday. I ordered an LP-XDS110ET, it will arrive in a couple of days. To my understanding, it will command our BP-CC3301 via JTAG. I don&#39;t see how it would shed light in the power limit array problem; can I really use a power limit array in the Radio tool?https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1681281/cc3351-tx-power-step-size-for-cc33xx/6480968Fri, 11 Sep 2026 13:24:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8f6305e5-372c-47ab-9b99-5c9221f0f648Dean RamsierThere are several interfaces related to TX power. Which one, exactly, are you referring to? If you are referring to the user facing interface to set TX power using iw, remember that passes through cfg80211 via nl80211, then mac80211 before it reaches the cc33xx driver. At the user level, the value is in mBm. But the mac80211/driver interface is specified in dBm, so mac80211 converts that value from mBm to dBm before sending it to the driver. By the time the power level reaches the cc33xx driver, the dBm value has already been established. See ieee80211_set_tx_power() in mac80211, and specifically the MBM_TO_DBM macro use within it.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1681555/cc3351-logger-pinFri, 11 Sep 2026 12:18:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:47453564-91d6-4d25-8a72-3a336010f820HS FAE GermanyPart Number: CC3351 Hi, what is the baud rate for reading out the logger pin? Is there any more decriptions / examples beside the logger_user_guide.html? Regards, Holgerbuilding automationCC3351https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1681281/cc3351-tx-power-step-size-for-cc33xxThu, 10 Sep 2026 19:34:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3240c9b1-205e-4096-beae-c08f6374f6a4Marinus HolznerPart Number: CC3351 Hi WiFi Apps team, Posting on customer behalve: We observed that the transmit power configuration in the driver is handled in integer dBm units, and in our current implementation the adjustment appears to be limited to 1 dBm steps. Could you please confirm whether this is the intended behavior for CC33XX? More specifically: Is the TX power setting for CC33XX officially defined in 1 dBm steps? Is there any TI documentation that describes the TX power adjustment granularity or rounding behavior? If the requested value is not exactly supported, is it rounded to the nearest valid step, or rounded down? We would appreciate any official guidance or documentation reference you can provide. Thank you, MarinusAppliancesCC3351https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1670104/cc3301-cc3301-band-edge-emissions/6479924Thu, 10 Sep 2026 18:28:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:1c132f0a-564f-47e9-8770-0d9bfbadb0c0Dylan HubbardHi Juha, I think I am following but let me double check - you confirmed the conf.bin you made with limited power is being correctly loaded since the Logger was effectively disabled with the ini parameter correct? I don&#39;t think I see the parameter asserted in the conf limited to 5 dBm. Are you able to use our Radio Tool with your system or do you have one of our EVKs by chance? I would like to see if using Radio Tool you are able to see the PLA operate as expected. This may be pointing to an issue with our RTOS SDK.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1669912/cc3351mod-lp-xds110et-with-bp-cc3351mod-stuck-in-get-device-type/6479914Thu, 10 Sep 2026 18:21:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a8e1724c-a02b-44d8-bf37-bea693da8c8bDylan HubbardHi Josef, 1. What version of the toolbox are you using? This bug should have been fixed for the latest version. 2. These descriptions are referring to different things - SWAU134A is explaining how to use an external clock sources from somewhere else, essentially removing the XTAL and providing a connection to the BP header.The datasheet advises leaving the pin unconnected so during Boot the device senses no external source and uses the internal slow clock.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1678701/cc3551e-unbricking-activating-brand-new-lp-em-cc35x1-using-segger-j-link-over-swd-lines-without-xds110/6479617Thu, 10 Sep 2026 15:12:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:db27d9e5-71cd-499e-8a1a-03927bc43fcaBLiuHi Swetha, You&#39;re setting the hash of the public key (root of trust) which is used to validate your signed images. No, it&#39;s not mandatory to set this up because you can choose authentication bypas. However, you must make a decision between auth bypass, SDK example key (TI provided), or vendor key (vendor created) and cannot change your mind afterwards. But yes, the chip&#39;s state must become DEPLOYED (can be achieved by any of the three options I mentioned) before any user application code can be programmed and executed.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1678701/cc3551e-unbricking-activating-brand-new-lp-em-cc35x1-using-segger-j-link-over-swd-lines-without-xds110/6479344Thu, 10 Sep 2026 11:26:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:aa8c3b6d-72a8-4f5a-9ff4-e1f0a71ca5e9Swetha DHello , We are currently designing a custom PCB utilizing a standalone CC3551E / CC35xx series Wi-Fi microcontroller chip sourced directly from the factory. Could you please confirm the following: When a raw CC3551E chip is populated on our own custom hardware for the first time, Is it mandatory to upload the Root of Trust certificate into the internal OTP eFuses and transition the chip&#39;s lifecycle state to &quot;DEPLOYED&quot; before any user application code can execute? Thank you for your guidance on this process.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1679587/cc3301-simplelink-wifi-toolbox-cli-command-delay-issue/6479313Thu, 10 Sep 2026 10:54:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:15ecc04d-8cb1-4bf0-9df4-21ca3bc737c4Jonathan CohenHello Jerry, The latest Toolbox release also supports REST API commands to execute Radio tool commands. This will be much faster than the CLI interface. Please see the Toolbox documentation in the &quot;docs&quot; folder, there is explanation on REST API commands, and example scripts. Regards, Jonathanhttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1669912/cc3351mod-lp-xds110et-with-bp-cc3351mod-stuck-in-get-device-type/6479153Thu, 10 Sep 2026 08:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4c97a513-ce34-4995-9f60-d8f67d464b10Josef G.Thank you for the confirmation! There is two more issues: 1. What is the difference between &quot;Load Default Containers&quot; and &quot;Load Custom Containers&quot; (when using prepopulated values in &quot;Load Custom Container&quot; scenario)? First option doesn&#39;t work: When selecting the &quot;Radio Tool&quot; we get stuck in &quot;Get Device Type&quot;. 2. Documentation issue: The documentation is not clear how to properly use the internal clock: The User guide SWAU134A states: The Y2 oscillator needs to be removed, and a 0201 sized 0-ohm resistor be populated on R29 pad . The datasheeet SWRS353A states: For this scenario, the SLOW_CLK_IN pin must be left not connected .https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1670104/cc3301-cc3301-band-edge-emissions/6479099Thu, 10 Sep 2026 08:01:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:060ced37-e91d-4c96-aa68-bfc288ba0abdJuha H&#228;m&#228;l&#228;inenI generated the conf with Toolbox 2.5.5 and 4.2.4 and the bin file was identical. A wrong toolbox version is not an issue now. We still haven&#39;t managed to get the power limit working on the PLT modes. I tried making a conf file filling the array with 5 dBm limit (0x0A) but no, full power comes out. You can see my conf file attached. e2e.ti.com/.../cc33xx_2D00_conf_5F00_verylow.tar We updated to the latest SDK, R9. We suspected if the conf file doesn&#39;t go to the CC3301. To verify that, I set the disable_logger setting, and the debug outputs stopped after the boot sequence. Consequently the conf file does affect. Our PLT mode is copied from your example project cc33xxx_network_terminal. We issue commands like power_mode on tune_channel 6 0 0 set_manual_calib -tx 1 -rx 1 set_tx -preamble_type 2 -phy_rate 5 -tx_power 30 -gi_ltf_type 2 -dcm 0 -length const packet 100 -delay 3000 -pkt_mode 0 -num_pkts 300 -data_mode 2 -data_const_val 85 -cca 1 -bss_color 13 -nominal_pkt_ext 1 -su_er_bw 0 -partial_aid 0 -feed_status 0 -aid 11 -src_addr 22:22:33:44:55:66 -dst_addr 02:02:03:04:05:06 start_tx If I adjust the tx_power, the output will obey up to 20 dBm even when the power limit array should kick in at 5 dBm. Here are two log captures from the debug output. One is for normal mode where our device joins Wi-Fi and tries to connect to AWS. Another is for the abovementioned PLT commands. Disable_debug is 0 in these. e2e.ti.com/.../logcaptures.ziphttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1680073/cc3235modasf-cc3235moda---telec-certificate/6479054Thu, 10 Sep 2026 07:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:833cec1c-d561-44a3-9530-6f4d8609347aRoger Meierok, much appreciated, thanks Josh!https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1670013/cc3351mod-acs-not-working-on-cc3351mod/6478568Wed, 09 Sep 2026 22:07:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:1194df9d-b7c5-40c1-8451-b5efa0062051David SoberanisHi Sabeeh, We will test the AP-based ACS you provided from hostapd2.0 and compare it with our AP-based ACS asap.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1665169/cc3351mod-m2-cc3351-streaming-video-crashes-cc3351-driver-part-2/6478563Wed, 09 Sep 2026 22:04:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d9d0cabb-ed91-4ae0-8bfe-5f92b0295285David SoberanisHi Dean and Sabeeh, Thank you for looking into this. [quote userid=&quot;313399&quot; url=&quot;~/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1665169/cc3351mod-m2-cc3351-streaming-video-crashes-cc3351-driver-part-2/6478258&quot;]It&#39;s possible but very unlikely. The reason why we don&#39;t support DFS channels is because the cc33xx first needs the ability to detect the radar signals on those channels. Once that is developed, then we can develop the rest of the capabilities for DFS support, such as moving channels, informing clients, etc.[/quote] [quote userid=&quot;605549&quot; url=&quot;~/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1665169/cc3351mod-m2-cc3351-streaming-video-crashes-cc3351-driver-part-2/6478331&quot;]Read $$$$ and additional scrutiny from the regulatory bodies.[/quote] Ah understood. This might be silly to ask, but are there any other 5 G channels besides 36, 40, 44, 48, 149, 153, 157, 161, and 165 that we can use?https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1680510/cc3351mod-can-cc3351mod-logs-be-toggled-output-to-sdio-instead-of-the-logger-pin/6478546Wed, 09 Sep 2026 21:54:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:df83e67e-a5fb-48fd-8ea8-1667df522abdDavid SoberanisHi Sabeeh, [quote userid=&quot;313399&quot; url=&quot;~/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1680510/cc3351mod-can-cc3351mod-logs-be-toggled-output-to-sdio-instead-of-the-logger-pin/6478139&quot;] Perhaps if it were connected to a UART-RX pin then it might work well for you.[/quote] Yes true. This will be changed in a future board revision, but sadly that will not happen soon. So I am trying to see if we can still receive and parse logs on AM62 given the situation. [quote userid=&quot;313399&quot; url=&quot;~/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1680510/cc3351mod-can-cc3351mod-logs-be-toggled-output-to-sdio-instead-of-the-logger-pin/6478139&quot;]I&#39;m still checking but I do not believe so. What baud rate would work for you?[/quote] Is 921600 or slower possible? [quote userid=&quot;313399&quot; url=&quot;~/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1680510/cc3351mod-can-cc3351mod-logs-be-toggled-output-to-sdio-instead-of-the-logger-pin/6478139&quot;]I believe the best way for us to collect the data in the other thread we are discussing, I would strongly suggest to use an FTD-like transceiver for the best experience. But yes I understand, getting the HW set up might be an issue for you.[/quote] Yes, I did this last year with the EVM. I am currently doing this again with the product. It would be ideal if we were able to access this logger pin without external hardware, since that would give our system detailed logs.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1673323/cc3551e-the-measured-ble-tx-power-of-cc3551-on-the-ti-evm-lp-em-cc35x1-is-low/6478498Wed, 09 Sep 2026 21:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c7fe01b4-5484-44c4-8402-876759b6ccebJosh SmithHi Alvin, I have attempted your issue on my own LP and I was able to replicate your issue. I found this to be caused by not having the 2nd USB C cable connected which would cause the device to not have enough current when performing at max power with the slow coded rate. Once I connected the 2nd cable, I was able to see results: However, what concerns me is that you mentioned that you have both USB C cables connected, but still having this issue. Can you share with me a picture of your setup? Can you ensure that both USB C cables are connected to the same source (i.e both connected to the same PC or laptop)? Best, Joshhttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1680302/cc3551e-ble-rx-le-1m-test-fail-on-the-ti-evm-lp-em-cc35x1-with-the-cc3551e/6478429Wed, 09 Sep 2026 20:19:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:db0ac309-7746-4896-8f36-8c8d52b4ae11Josh SmithHey Jesse, I will be looking into this by talking to a few BLE experts on our team. In the mean time, do you know if they have tried a LP to LP configuration? Do they experience the same issue of receiving incorrect packets? If not, can you have them try this configuration? Best, Joshhttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1680073/cc3235modasf-cc3235moda---telec-certificate/6478408Wed, 09 Sep 2026 20:00:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f9b82e2f-1cd4-4d27-8a1f-56c9eec30266Josh SmithHi Roger, CC3235MODASF shares the same TELEC certificate and ID as the CC3235MODSx versions. You should be able to just provide that certificate alongside our datasheet that lists CC3235MODAx as part of the 201-190033 ID. Best, Joshhttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1665169/cc3351mod-m2-cc3351-streaming-video-crashes-cc3351-driver-part-2/6478331Wed, 09 Sep 2026 19:06:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e0812597-3570-49ac-b381-e42ca369e09aDean RamsierDavid Soberanis Also, assuming the very unlikely case it were to be developed, keep in mind that it will incur additional regulatory burden to validate, and it will vary in different jurisdictions. Read $$$$ and additional scrutiny from the regulatory bodies.