• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 42 subscribers
  • Views 228 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3351: After disabling Wi-Fi 6, the AC mode is malfunctioning.

yixiong lin
Prodigy 170 points

Part Number: CC3351

Hi TI experts

    After disabling Wi-Fi 6, I noticed that the 802.11ac mode also disappeared. Specifically, I can no longer detect the  RF signal for ac mode, and the logs captured with the network packet capture tool no longer show VHT either. Why is this happening? I disabled Wi-Fi 6 by setting HE_Enable to 00 in the cc33xx-conf.bin file.

Fw Version 1.7.11.323 

Driver Version 1.7.2.239

PHY version 1.2.0.47.6.6.39.69

image.png

 

  • 0
    TI__Mastermind 35300 points

    Hi Yixiong,

    Sorry, I deleted my previous reply because it is actually incorrect.

    Our firmware implements wifi 5 and wifi 6 features together, as we do support 80 mhz channel width. So we only support wifi 4 and wifi 6 modes.

  • 0 in reply to Sabeeh Khan1
    Prodigy 170 points

    Hi Sabeeh

      Thank you for your reply. However, after disabling Wi-Fi 6, Wi-Fi 5 is also gone, which does not meet our requirements. We still need Wi-Fi 5. Is there any way to resolve this issue?

  • 0 in reply to yixiong lin
    TI__Mastermind 35300 points

    Hi Yixiong,

    We don't have an easy method to resolve this issue, and we were not aware of this requirement. It will take several months to develop something like this.

    Can you please explain in detail of why you need this requirement?

  • 0 in reply to Sabeeh Khan1
    Expert 1721 points

    It might be sufficient to leave wi-fi6 enabled in the conf file, and simply not declare support in the driver by not populating the iftype information. 

    Looks like that can be done by in cc33xx_init_ieee80211() by just taking 'else' clause here:

        if((!wl->disable_wifi6) && (wl->conf.mac.he_enable))
        {
            wl->hw->wiphy->iftype_ext_capab = he_iftypes_ext_capa;
            wl->hw->wiphy->num_iftype_ext_capab =
                ARRAY_SIZE(he_iftypes_ext_capa);
        }
        else
        {
            cc33xx_band_2ghz.iftype_data = NULL;
            cc33xx_band_2ghz.n_iftype_data = 0;

            cc33xx_band_5ghz.iftype_data = NULL;
            cc33xx_band_5ghz.n_iftype_data = 0;
        }
    Add a '0 &&' to that if statement, and it might just work.
    This way you keep the vht info, but have removed the HE info that comes in with iftype. It isn't completely disabled in firmware, but if HE support isn't declared to external APs or the supplicant it shouldn't get used...
  • 0 in reply to Dean Ramsier
    Prodigy 170 points

    Have you validated this approach? Are there any risks associated with it?

  • 0 in reply to yixiong lin
    Expert 1721 points

    I have not. I'm not TI, and I have no reason to disable HE operation. I'm just giving you a possible option, you can do with it as you wish.

  • 0 in reply to Dean Ramsier
    Prodigy 170 points

    Thank you

     Hi Sabeeh 

        From TI's perspective, do you think this approach is feasible? We want to keep Wi‑Fi 5 mainly because our previous generation products also had it, and we would like to maintain as much consistency as possible.

  • 0 in reply to yixiong lin
    TI__Mastermind 35300 points

    Hi Yixiong,

    It does make sense to simply remove HE capabilities from the driver using the approach Dean listed above. I don't see risks with it, but I have not tested it either. Note that you are now straying away from TI driver/SDK so you must now manage and maintain this change yourself across the kernel versions you are supporting. 

    As a note, we are discussing internally how to break VHT and HE apart in the firmware, so let's discuss in our meetings if this is a hard requirement for your application. Until then, I suggest to leave HE enabled and the driver unchaged.