Wi-Fi Bluetooth for Linux

Hi @AnjanaM_61 

https://community.infineon.com/t5/AIROC-Wi-Fi-and-Wi-Fi-Bluetooth/Queries-about-CYW43XXX-series-chipsets/m-p/338439#M935 

I cannot give reply over there (above link) so continuing my question here.

As by your answer (3rd point), other options for HFP and A2DP were Linux  or Android. So, both the chipsets CYW4343W and CYW43012 support HFP and A2DP. So, kindly send me the links of respective SDKs, so that I can evaluate and finalize the chipset for our application.  

And please be noted that, in Linux  and Android SDKs must contain A2DP, HFP and HSP supporting SBC and AAC codecs.

Thanks and Regards.

Vinayak

My setup:

- ARM host processor running 5.10 Linux. 

- Murata 1MW BT/Wi-Fi combo chip (BCM43455) over SDIO

- Wi-Fi firmware: version 7.45.249

- Using linux/hostapd patch sets from "cypress-fmac-v5.10.9-2022_0511"

The issue:

After removing the brcmfmac kernel module, Bluetooth performs very poorly (drops active connections, scan no longer detects devices, sco audio is extremely crackly if the connection does not drop, etc.). This is only observed if Wi-Fi was associated to an AP within 3 seconds of kernel module removal. Re-inserting the module always corrects the issue. 

Example steps to reproduce the issue:

- Start with brcmfmac modules loaded and associated to an AP, then run the following in a script:

ifdown wlan0

modprobe -r brcmfmac

- Bluetooth performs poorly

Then, I ran the following test:

- Start with brcmfmac modules loaded and associated to an AP, then run the following in a script:

wpa_cli disconnect

sleep 3

ifdown wlan0

modprobe -r brcmfmac

- Bluetooth functions normally.

Once I realized a 3 second delay after disconnect prevented the issue, I investigated to see how late in the module removal the delay could be placed before the issue began to occur again. I tried moving the delay into the kernel module itself and found that as long as the 3 second delay is put before the call to brcm_chip_set_passive() made in brcmf_sdio_remove(), then the issue is avoided. If I place it after that call, then I experience the poor Bluetooth performance. 

It seems like the module is left in a state where Bluetooth is in low priority.  Perhaps the module is still attempting to disassociate with the network when the chip is placed in passive mode? I am trying to understand what is happening so that I can avoid this issue properly, rather than inserting a long delay and hoping it is always sufficient. 

Any insight as to what is happening would be greatly appreciated. It is difficult to find information on the BT/Wi-Fi coexistence mechanism used by this chip. 

Thank you,

For emissions testing, I am trying to use the wl tool with NVIDA Jetson TX2, which has the BCM4354. I received a wl64 executable and 4354’s mfgtest firmware from an Infineon Tech Support Case.

I believe I correctly installed the mfgtest firmware by replacing /lib/firmware/brcm/fw_bcmdhd.bin with cyfmac4354-sdio.bin and by moving cyfmac4354-sdio.clm_blob to become /lib/firmware/brcm/bcmdhd.clm_blob. Before the above changes, running “sudo ./wl64 ver” gave me:

1.28 RC0.0
wl0: Jul 21 2020 16:35:45 version 7.35.349.94 (r726700 CY) FWID 01-aa356e32

After installing mfgtest firmware, the wl ver command gave me:

1.28 RC0.0
wl0: Sep  1 2021 02:23:00 version 7.35.349.112 (ae8cc29 CY WLTEST) FWID 01-6e1af42a

My main problem is that wl64 can’t bring up the Wi-Fi after I use it to bring down the Wi-Fi. It also doesn't work using the original firmware (i.e., before introducing the mfgtest firmware). The following are the commands I ran and the output.

user@device:~$ ip -br address show wlan0
wlan0            UP             192.168.0.79/24
user@device:~$ sudo ./wl64 down
user@device:~$ ip -br address show wlan0
wlan0            DORMANT        192.168.0.79/24

(after ~20 seconds)

user@device:~$ ip -br address show wlan0
wlan0            DORMANT
user@device:~$ sudo ./wl64 up
user@device:~$ ip -br address show wlan0
wlan0            DORMANT

At this point, I also can’t use the GUI to connect to a Wi-FI network.

Have I done anything wrong? What do I do so that I can at least use the wl tool to bring down and up the Wi-Fi module?

Package Version

v5.10.9-2022_0511

Release Date

2022-05-11

Description

This is Cypress's Linux brcmfmac driver and firmware support package.
Brcmfmac is an open-source driver project.

Files in this release:
* Backports package (cypress-backports-v5.10.9-2022_0511-module-src.tar.gz)
* Firmware/clm_blob files (cypress-firmware-v5.10.9-2022_0511.tar.gz)
* Cypress fmac patch files (cypress-patch-v5.10.9-2022_0511.tar.gz)
* Device tree files (cypress-devicetree-2022-05-13.tar.gz)
* hostapd/wpa_supplicant patch (cypress-hostap_2_9-1-2022_0511.tar.gz)
* Cirrent Agent (cypress-cirrent-1.60.tar.gz)
* Documents (docs/)
* README

Checksum

sha256sum: 
7cf529c371f0bc8c47908c42359879aee308970b34e7c5e971bd9a79124f215b  cypress-backports-v5.10.9-2022_0511-module-src.tar.gz
ce3bb31020e5ffe24fe549802440c137d14a05ad77af3e8e1fb9e184db96ed55  cypress-cirrent-1.60.tar.gz
4bce8d957b451f7d9a23bd77121eea920bde372f6097424c6e87d6a61aa34d9e  cypress-devicetree-2022-05-13.tar.gz
8b301a0828f4eecfc261039bff01a875edc0f93c58887814941b7cdfbe8bacb8  cypress-firmware-v5.10.9-2022_0511.tar.gz
ca748efbef2b6197a50152e3d51fb028949be5bbcb2474b67e2e35dd5aa1804f  cypress-hostap_2_9-1-2022_0511.tar.gz
8201ad2e8720279f5baf870be57fe15be49d714bcaa0653c0faa8de80b8a2c51  cypress-patch-v5.10.9-2022_0511.tar.gz
ec1311ceddd80e3a24dbf2976cbbfbb043d7909d8cd91c4254da563d3dedf9e8  README.txt

 [Change Log]

2022-06-07 Initial Post

Hi All,

We are using CYW43012 chipset and recently moved from:
Firmware version:
1.21 RC0.0
wl0: Sep 1 2021 22:33:32 version 13.10.271.273 (9278a67 CY) FWID 01-e6c8687a
Driver Version:
Backported Linux Version v4.14.77-kong-RTM-rc8-0-ged6fa18

to

Firmware version:
1.21 RC0.0
wl0: Feb 21 2022 07:19:28 version 13.10.271.283 (211da63 CY) FWID 01-18f4ac2
Driver Version:
Backported Linux Version v5.10.9-2022_0321-0-ga0971bc0b123

We found that the DFS channel support for US country is currently disabled in the latest release where as it was working in the older release.

Old release:

root@SAMA5D2C3:~# wl ver
1.21 RC0.0
wl0: Dec 13 2019 03:35:44 version 13.10.271.227 (6ca6a80) FWID 01-396d897 tws:GENR.3.1.2
root@SAMA5D2C3:~# wl country
US (US/0) UNITED STATES
root@SAMA5D2C3:~# wl channels
36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165
root@SAMA5D2C3:~# wl chan_info
Channel 36 A Band
Channel 40 A Band
Channel 44 A Band
Channel 48 A Band
Channel 52 A Band, RADAR Sensitive
Channel 56 A Band, RADAR Sensitive
Channel 60 A Band, RADAR Sensitive
Channel 64 A Band, RADAR Sensitive
Channel 100 A Band, RADAR Sensitive
Channel 104 A Band, RADAR Sensitive
Channel 108 A Band, RADAR Sensitive
Channel 112 A Band, RADAR Sensitive
Channel 116 A Band, RADAR Sensitive
Channel 120 A Band, RADAR Sensitive
Channel 124 A Band, RADAR Sensitive
Channel 128 A Band, RADAR Sensitive
Channel 132 A Band, RADAR Sensitive
Channel 136 A Band, RADAR Sensitive
Channel 140 A Band, RADAR Sensitive
Channel 144 A Band, RADAR Sensitive
Channel 149 A Band
Channel 153 A Band
Channel 157 A Band
Channel 161 A Band
Channel 165 A Band
root@SAMA5D2C3:~#

New Release:

root@SAMA5D2C3:/etc/broadcom/wifi# wl country
US (US/0) UNITED STATES
root@SAMA5D2C3:/etc/broadcom/wifi# wl channels
36 40 44 48 149 153 157 161 165
root@SAMA5D2C3:/etc/broadcom/wifi# wl chan_info
Channel 36 A Band
Channel 40 A Band
Channel 44 A Band
Channel 48 A Band
Channel 149 A Band
Channel 153 A Band
Channel 157 A Band
Channel 161 A Band
Channel 165 A Band

Using the old clm_blob file is working fine with the new release. Can you please let us know how to reenable DFS channels and any other parameters in the new release?

@raks_99 

Regards,

Rupesh

Hi All,

We are using CYW43012 chipset and recently moved from:
Firmware version:
1.21 RC0.0
wl0: Sep 1 2021 22:33:32 version 13.10.271.273 (9278a67 CY) FWID 01-e6c8687a
Driver Version:
Backported Linux Version v4.14.77-kong-RTM-rc8-0-ged6fa18

to

Firmware version:
1.21 RC0.0
wl0: Feb 21 2022 07:19:28 version 13.10.271.283 (211da63 CY) FWID 01-18f4ac2
Driver Version:
Backported Linux Version v5.10.9-2022_0321-0-ga0971bc0b123

We are seeing increase in power consumption by 20mA approximately after we upgrade the release.

We have observed that only by changing the driver the power consumption increases but not with the firmware upgrade.

We couldn't figure out what exactly caused increase in the power cosumption.

Can someone help us figure out the reason for the same as our product is an battery powered embedded device which makes it very critical for us.

Please let me know if you need any information.

@raks_99 @GauravS_31 @Vinayak 

Regards,

Rupesh

Hello,

As part of the industrialization of a project, I want to pass the compule module 4 card in a certification laboratory.

I developed a distribution using yocto. I am looking for an application that allows the wifi module of the compute module 4 to be transmitted.

I need to make the module transmit at 2.4GHz at the minimum, center and maximum frequency.

I have to do the same with both frequencies in 5GHz. (minimum, central and maximum)

Do you have an ARM application and commands that allow me to do this?

Thank a lot.

Arthur