I'm using BCM4354 wifi module in our product. For FCC compliance testing I need to put the module in continuous transmission in the following modes - 802.11b, g, n(20MHz), n(40MHz) and ac. By referring the Cypress Wi-Fi CLM Regulatory Manual.pdf I was able to do the same. However, I have few concerns in the testing. Kindly, help me in resolving the below 2 issues.
$ wl chanspec -c 1 b 2 -w 40 -s 1 -> channel-1, operating band-2.4GHz, bandwidth - 40MHz
Is this module limitation?
Anticipating your quick response.
1. The transmission power to be set depends on what region that you are planning to ship to and the regulatory restrictions set in that region.
2. Could you post the wl clmver output and the country code to check if it is enabled or not? Ideally it should be enabled. This is for us to confirm.
I believe the country code must be set to ALL while performing the compliance testing as per the Cypress Wifi Regulatory guide. But, if I set the country as ALL, I'm getting an error as shown below,
$ wl country ALL
wl: error -2
Since our product is being deployed in the US, I'm using wl country US/0 command to set the country code.
This is the output I got for wl clmver.
Customization: v1 200611
Creation: 2020-06-11 09:54:15
The country code "all" is missing in the firmware which you are using. We are in the process to fix this issue. In the meantime, you can use the following release: Cypress-Linux-WiFi-Driver-Release-FMAC-2020-04-02
Let me know if you have any concerns.
Hi @YashM ,
Thanks for the new firmware release. With the new clm_blob I was able to set the country code to ALL and 802.11n40 in 2.4GHz band also started working.
But I'm not able to select the output antenna when testing 5GHz in mimo mode for 802.11n and ac standards. I'm getting the below error while running the txant command with the wl tool to select the antenna.
$ wl txant 1
wl: error -23
Unfortunately, "wl txant" doesn't work with MIMO devices.
Instead, you can use wl txchain <value> (1 = chain 0, 2 = chain 1, 3 = chain 0 and 1).
Also, you can see the wl command sequence in Cypress's Regulatory manual section 126.96.36.199.
Let me know whether this solves your problem or not.